home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Nebula 2
/
Nebula Two.iso
/
SourceCode
/
MiscKit1.7.1
/
MiscKitArchive.mbox
/
mbox
/
000126_misckit-reques…aska.et.byu.edu_Wed Feb 16 00:52 MST 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-10-30
|
2KB
Received: from YVAX2.BYU.EDU by maine.et.byu.edu; Wed, 16 Feb 1994 00:52:27 -0700
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-4 #4169)
id <01H8XNM63I34984I6W@yvax.byu.edu>; Wed, 16 Feb 1994 00:52:23 MST
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-4 #4169)
id <01H8XNM2GT1S02HXEI@yvax.byu.edu>; Wed, 16 Feb 1994 00:52:18 MST
Received: from yvax1.byu.edu by alaska.et.byu.edu; Wed,
16 Feb 1994 00:49:18 -0700
Received: from DIRECTORY-DAEMON by yvax.byu.edu (PMDF V4.3-4 #4169)
id <01H8XNI5X7V4984I6W@yvax.byu.edu>; Wed, 16 Feb 1994 00:49:09 MST
Received: from alaska.et.byu.edu by yvax.byu.edu (PMDF V4.3-4 #4169)
id <01H8XNI34T0G02HXLJ@yvax.byu.edu>; Wed, 16 Feb 1994 00:49:05 MST
Received: by alaska.et.byu.edu; Wed, 16 Feb 1994 00:48:57 -0700
Date: Wed, 16 Feb 1994 00:48:57 -0700
From: yackd@alaska.et.byu.edu (Don Yacktman)
Subject: Maturity index
To: misckit@byu.edu
Message-id: <199402160748.AAA15934@alaska.et.byu.edu>
Content-transfer-encoding: 7BIT
Status: RO
In the Brad Cox book on Obj-C, p. 109, it is suggested that the spec
sheet for an object should contain a "maturity index" that tells how
old/well tested an object is. That gives users an idea of how much
trust can safely be placed in an object and provides a feel for how
stable the design/implementation are and so on.
I think it would probably be a good idea to add such a metric to the
class documentation in the MiscKit as the kit becomes more diverse
to keep things more useable. However, the question comes up as to
what maturity levels should be used and what they mean. What is an
immature object, versus mature? How many shades of maturity should
be used? Is this even worth discussing? :-)
I'd like to hear thoughts on this...it would be potentially useful
to people, I believe. Right now most of the kit is (IMHO) still
somewhat immature, but that's only IMHO, others would disagree in
some areas I suspect. So let's hear some ideas on this. If it
helps to set up a scale, we can try and classify some of the kit
objects, perhaps. (Oh, and maybe a single metric is too simplistic;
we are talking both code and design maturity, at least. Maybe both
should be kept separate.)
What do you think?
Later,
-don